Cycling faster through the list
Original Post
With all of Mark Forster's systems, I have always struggled to cycle through the list fast enough. If I don't cycle fast enough, I can end up "chasing the end of the list" and never revisiting the beginning of the list. Even if I do cycle through from time to time, infrequent cycling means infrequent exposure to the items in my list. My list will work better if I am constantly exposed to its contents; the subconscious mind will always be processing them in the background. Also, infrequent cycling means I won't trigger the "dismissal" rules, which means I will be lacking one of the key ingredients of Mark Forster's systems.
Here are some rule modifications that have helped me cycle through the list faster, in order of most effective to least effective (in my experience at least). These modifications assume one is using the standard SF3 rules ( http://www.markforster.net/blog/2011/2/10/rules-for-superfocus.html ).
1. OVERCOME YOUR FEAR OF DISMISSAL. Seriously. Fear of dismissal can cause you to "game" the system and play tricks to prevent a page from getting dismissed. Reflecting on dismissed items is one of the most powerful, even life-changing, elements of Mark Forster's systems. Don't deprive yourself of its power. Let "standing out" and "dismissal" do their work.
2. Set a time limit to get through each page so that you will cycle through your notebook at least once per day. E.g., if you have 12 active pages, and 8 hours of discretionary time per day, then set a time limit of 8/12 = 40 minutes per page. Set a timer, and move on when the timer rings. If you haven't actioned anything in Column 1 yet, then dismiss everything left on the page. I don't LIKE using this rule, since using a timer just feels "kludgey" and awkward. But since it *IS* so effective, I do use it if I seem to be moving too slowly and need a kick-start.
3. Enter urgent items into Column 2 on the NEXT page instead of the current page. (If it makes you anxious to put it on the next page, because you think you won't get to it quickly enough, then go ahead and put it on the current page -- but your default should be to enter it on the NEXT page.)
4. When you come to a new page, take action on all items in Column 2 before looking at the items in Column 1.
5. Use a notebook with more lines per page. (This did seem to make a slight difference when I moved from a 22-line pocket notebook to a 5"x8" 32-line notebook. But only a SLIGHT difference. If you like the convenience and portability of a pocket notebook, I would not recommend switching to a larger notebook simply in order to get more speed. I am planning to switch back to a pocket notebook after I finish up my current 5x8 notebook.)
Here are other ideas I tried to increase cycling speed -- they didn't seem to help. (They DID help reduce "overloading" Column 2, but did not seem to make any difference in cycling speed):
+ Make daily Column 2 tasks into daily habits so you do them as part of your daily routine instead of in SF (e.g., checklist at beginning of day)
+ Use notebook with FEWER lines per page. In my experience this made the cycling time slower, not faster. But the difference was only slight.
+ Block off a few lines of Column 1 on every page (so that Column 2 will have more lines than Column 1). This didn't make any difference to cycling time.
+ De-commission Column 2 tasks back to Column 1, especially if priorities have changed. This helped keep Column 2 "leaner", which did increase cycling time, but it's a bad habit to get into, if you are following the standard SF3 rules. It takes away the whole reason behind Column 2 and eventually Column 2 loses its "kick". (If you *like* that idea, then you can try Mark Forster's latest variation -- http://www.markforster.net/forum/post/1453964 ).
I also tried this idea but it seriously disturbed the "flow" of the list -- it just wasn't "SuperFocus" any more:
+ Act on no more than 1 item in C1 during each visit to the page. This might work in an "emergency" but I would not recommend it as a general habit. It is just far too constricting.
Has anyone tried any other minor rule modifications that preserve the "flow" and overall effectiveness of SuperFocus, but help improve the cycling speed?
Here are some rule modifications that have helped me cycle through the list faster, in order of most effective to least effective (in my experience at least). These modifications assume one is using the standard SF3 rules ( http://www.markforster.net/blog/2011/2/10/rules-for-superfocus.html ).
1. OVERCOME YOUR FEAR OF DISMISSAL. Seriously. Fear of dismissal can cause you to "game" the system and play tricks to prevent a page from getting dismissed. Reflecting on dismissed items is one of the most powerful, even life-changing, elements of Mark Forster's systems. Don't deprive yourself of its power. Let "standing out" and "dismissal" do their work.
2. Set a time limit to get through each page so that you will cycle through your notebook at least once per day. E.g., if you have 12 active pages, and 8 hours of discretionary time per day, then set a time limit of 8/12 = 40 minutes per page. Set a timer, and move on when the timer rings. If you haven't actioned anything in Column 1 yet, then dismiss everything left on the page. I don't LIKE using this rule, since using a timer just feels "kludgey" and awkward. But since it *IS* so effective, I do use it if I seem to be moving too slowly and need a kick-start.
3. Enter urgent items into Column 2 on the NEXT page instead of the current page. (If it makes you anxious to put it on the next page, because you think you won't get to it quickly enough, then go ahead and put it on the current page -- but your default should be to enter it on the NEXT page.)
4. When you come to a new page, take action on all items in Column 2 before looking at the items in Column 1.
5. Use a notebook with more lines per page. (This did seem to make a slight difference when I moved from a 22-line pocket notebook to a 5"x8" 32-line notebook. But only a SLIGHT difference. If you like the convenience and portability of a pocket notebook, I would not recommend switching to a larger notebook simply in order to get more speed. I am planning to switch back to a pocket notebook after I finish up my current 5x8 notebook.)
Here are other ideas I tried to increase cycling speed -- they didn't seem to help. (They DID help reduce "overloading" Column 2, but did not seem to make any difference in cycling speed):
+ Make daily Column 2 tasks into daily habits so you do them as part of your daily routine instead of in SF (e.g., checklist at beginning of day)
+ Use notebook with FEWER lines per page. In my experience this made the cycling time slower, not faster. But the difference was only slight.
+ Block off a few lines of Column 1 on every page (so that Column 2 will have more lines than Column 1). This didn't make any difference to cycling time.
+ De-commission Column 2 tasks back to Column 1, especially if priorities have changed. This helped keep Column 2 "leaner", which did increase cycling time, but it's a bad habit to get into, if you are following the standard SF3 rules. It takes away the whole reason behind Column 2 and eventually Column 2 loses its "kick". (If you *like* that idea, then you can try Mark Forster's latest variation -- http://www.markforster.net/forum/post/1453964 ).
I also tried this idea but it seriously disturbed the "flow" of the list -- it just wasn't "SuperFocus" any more:
+ Act on no more than 1 item in C1 during each visit to the page. This might work in an "emergency" but I would not recommend it as a general habit. It is just far too constricting.
Has anyone tried any other minor rule modifications that preserve the "flow" and overall effectiveness of SuperFocus, but help improve the cycling speed?
Reply by Anthony
Hi Seraphim,
As ever, your posts are thought provoking and this one really resonates for me.
I really struggle to dismiss, and I "game" the system to avoid dismissing. As a result I tend to only put actions on the list that have to be done rather than throwing everything at the system. I know that as a consequence I am massively diluting the power of the system.
That said, the system still works really well for me in terms of being productive - its just that I'm conscious that it could be a whole lot more powerful.
Your tips are all interesting - but for me tip number 1 is the real issue. Looking forward to putting it into action.......
As ever, your posts are thought provoking and this one really resonates for me.
I really struggle to dismiss, and I "game" the system to avoid dismissing. As a result I tend to only put actions on the list that have to be done rather than throwing everything at the system. I know that as a consequence I am massively diluting the power of the system.
That said, the system still works really well for me in terms of being productive - its just that I'm conscious that it could be a whole lot more powerful.
Your tips are all interesting - but for me tip number 1 is the real issue. Looking forward to putting it into action.......
Reply by Mark Forster
I always have a problem envisaging what it is that causes crawlers to crawl because it is so alien to my own way of working the list. And I often wish that I could stand over someone's shoulder so I could tell them what they are doing wrong.
I think it's important to pay particular attention to two of the rules. One is dismissal, which as Seraphim says above is a key element of the system. I can't stress enough how important this is.
The second is "standing out" or "feeling ready to be done". The whole idea is that your mind should act intuitively within the framework of the rules, not consciously. If you find yourself making calculations like "if I do three tasks on this page, I'll reach x in time to meet the deadline", you are not working SF properly.
However just because you are working "intuitively" doesn't mean that you have no control over what you are doing. You can instruct your intuition so that it achieves what you want it to.
In particular you need to instruct your intuition about what speed it should be going at. There is a continuum between CRAWL and RACE, and you should be considerably nearer the RACE end than the CRAWL end. It's actually no more difficult to decide to speed up while doing SF than it is to decide to quicken your pace when you are walking down the street.
I think it's important to pay particular attention to two of the rules. One is dismissal, which as Seraphim says above is a key element of the system. I can't stress enough how important this is.
The second is "standing out" or "feeling ready to be done". The whole idea is that your mind should act intuitively within the framework of the rules, not consciously. If you find yourself making calculations like "if I do three tasks on this page, I'll reach x in time to meet the deadline", you are not working SF properly.
However just because you are working "intuitively" doesn't mean that you have no control over what you are doing. You can instruct your intuition so that it achieves what you want it to.
In particular you need to instruct your intuition about what speed it should be going at. There is a continuum between CRAWL and RACE, and you should be considerably nearer the RACE end than the CRAWL end. It's actually no more difficult to decide to speed up while doing SF than it is to decide to quicken your pace when you are walking down the street.
Reply by DavidC
I think that the discussion of cycle rates/processing speed so far has neglected the fact that the items put on the SF list by different people will vary in terms of the time they take to complete.
My own list has no shortage of tasks that won't take long. "Call Emma"; "Pay for printer".
It also has tasks that will take a few hours. "John lunch" will be about 3 hours, by the time I've agreed with him a convenient date, arranged the booking, travelled to the venue, had lunch with him, travelled back to the office, and written a file note on what was discussed.
Yet other items will take days. Some are recreational: "K wants to go to Venice". [K is the girlfriend.] Others are work projects: "Market entry strategy for Canada", that make best progress with focussed attention for anywhere between an afternoon and a whole day, and will probably take a week of effort to write.
Taking these things together, I'm finding that I'm moving forward or compleiting 8-10 items in what remains of a day after scheduled meetings. There are 388 items on the list at the moment. That means it would take at least 39 days to complete the list, and that assumes everything gets deleted as a result of being completed first time it is visited, and nothing new comes in.
You simply aren't going to get round a list that has that much on it in a day or two, unless your interpretation of dismissal is that you should dismiss anything that you have no reasonable prospect of getting to within, say, a week. But if you dismiss like that, you'll wind up completing reactive items at the expense of long run, carefully thought-through goals. I actively want long run projects on the list, as subjecting them to little and often processing will get them done eventually.
My own list has no shortage of tasks that won't take long. "Call Emma"; "Pay for printer".
It also has tasks that will take a few hours. "John lunch" will be about 3 hours, by the time I've agreed with him a convenient date, arranged the booking, travelled to the venue, had lunch with him, travelled back to the office, and written a file note on what was discussed.
Yet other items will take days. Some are recreational: "K wants to go to Venice". [K is the girlfriend.] Others are work projects: "Market entry strategy for Canada", that make best progress with focussed attention for anywhere between an afternoon and a whole day, and will probably take a week of effort to write.
Taking these things together, I'm finding that I'm moving forward or compleiting 8-10 items in what remains of a day after scheduled meetings. There are 388 items on the list at the moment. That means it would take at least 39 days to complete the list, and that assumes everything gets deleted as a result of being completed first time it is visited, and nothing new comes in.
You simply aren't going to get round a list that has that much on it in a day or two, unless your interpretation of dismissal is that you should dismiss anything that you have no reasonable prospect of getting to within, say, a week. But if you dismiss like that, you'll wind up completing reactive items at the expense of long run, carefully thought-through goals. I actively want long run projects on the list, as subjecting them to little and often processing will get them done eventually.
Reply by Alan Baljeu
Hi Dave. I'm wrestling with these ideas myself. I think the idea is that you don't want 389 things on your list. You want maybe half that. To get to there, move faster through the list, and if that means something important is dismissed, that's okay.
The dismissing of pages doesn't mean the rejecting of tasks. It means setting aside tasks that aren't presently worth your worrying about. After all, 180 are plenty to keep you occupied and you'll be more effective. And then through regular review you can bring some of the others back in again later when you've set finshed some of the current load.
The dismissing of pages doesn't mean the rejecting of tasks. It means setting aside tasks that aren't presently worth your worrying about. After all, 180 are plenty to keep you occupied and you'll be more effective. And then through regular review you can bring some of the others back in again later when you've set finshed some of the current load.
Reply by Erik
Dave:
SF is a Task" Management system.
What you need is a "Projects" Management system that will feed SF at the appropriate time with sizable chunks tasks.
-My 2 cents
@everybody
As Mark and Seraphim says: Embrace Dismissal!
SF is a Task" Management system.
What you need is a "Projects" Management system that will feed SF at the appropriate time with sizable chunks tasks.
-My 2 cents
@everybody
As Mark and Seraphim says: Embrace Dismissal!
Reply by Hugo Ferreira
The "problem" I'm having that slows me a lot has to do with tasks like coding/programming where the "little" part of "little and often" can easily be 45min to an hour (minimum), and the "work as long you feel like" can to for 4 or 5 hours without even noticing (fully focused; in the "zone").
This can be specially relevant when chasing bugs in code your didn't wrote. Just the preparation part (replicate the scenario; get the flow in your head), to get to a point where you can start working the problem, takes a long time and is not much reusable: stoping work would imply having to repeat a lot of the preparation again when you came back to it (if time away was not long), or even doing it all over again (if time the away was longer, e.g. the next day/days).
This can be specially relevant when chasing bugs in code your didn't wrote. Just the preparation part (replicate the scenario; get the flow in your head), to get to a point where you can start working the problem, takes a long time and is not much reusable: stoping work would imply having to repeat a lot of the preparation again when you came back to it (if time away was not long), or even doing it all over again (if time the away was longer, e.g. the next day/days).
Reply by Mark Forster
DavidC:
Is the way you are working at the moment producing the results you want? If so, then ignore what I am about to say and just carry on doing what you're doing..
If it's not, then you will need to accept that some things will have to change. In which case my advice is:
a) split your longer tasks/projects up into shorter steps;
b) increase your speed so you get through your list at least once a day;
c) allow dismissal to reduce the number of tasks/projects you are actively working on.
Is the way you are working at the moment producing the results you want? If so, then ignore what I am about to say and just carry on doing what you're doing..
If it's not, then you will need to accept that some things will have to change. In which case my advice is:
a) split your longer tasks/projects up into shorter steps;
b) increase your speed so you get through your list at least once a day;
c) allow dismissal to reduce the number of tasks/projects you are actively working on.
Reply by Mark Forster
Hugo:
You haven't said why you regard this as a problem. Doing coding is your job, so you've given an example of doing your job. There's only a problem if you are not succeeding in doing your job.
You haven't said why you regard this as a problem. Doing coding is your job, so you've given an example of doing your job. There's only a problem if you are not succeeding in doing your job.
Reply by Bernie
I think Hugo is describing my situation, if I understand properly.
When I am on this sort of project, the "problem" is that I struggle to work little & often, and I move very slowly through the list.
For me, this type of project describes a part of what I do. Some days, or stretches of days, it dominates. That's when I become one of the "crawlers." On days when I don't work one of these projects, I am a racer.
On these bigger projects, yes I am doing my job by getting the big things done. But meanwhile I am dropping the little things on the floor; and if there are no urgent little things floating around, then I am in constant anxiety that there might be.
SF promised to help (and does!) with its "little and often," but this type of project is the one that I am still struggling to learn to manage. One thing I've learned so far: when I get *stuck*, turn to SF instead of bashing against the wall. It is very helpful! But when I don't get stuck, I can easily blink to find it is 10:00pm, and then if I haven't seen the following pages of my list in a while, I get this vague feeling that I may have missed something.
I suppose time-boxing is in order for us then. I've been brainstorming on some approaches for next week.
When I am on this sort of project, the "problem" is that I struggle to work little & often, and I move very slowly through the list.
For me, this type of project describes a part of what I do. Some days, or stretches of days, it dominates. That's when I become one of the "crawlers." On days when I don't work one of these projects, I am a racer.
On these bigger projects, yes I am doing my job by getting the big things done. But meanwhile I am dropping the little things on the floor; and if there are no urgent little things floating around, then I am in constant anxiety that there might be.
SF promised to help (and does!) with its "little and often," but this type of project is the one that I am still struggling to learn to manage. One thing I've learned so far: when I get *stuck*, turn to SF instead of bashing against the wall. It is very helpful! But when I don't get stuck, I can easily blink to find it is 10:00pm, and then if I haven't seen the following pages of my list in a while, I get this vague feeling that I may have missed something.
I suppose time-boxing is in order for us then. I've been brainstorming on some approaches for next week.
Reply by Seraphim
Mark wrote:
<< I always have a problem envisaging what it is that causes crawlers to crawl because it is so alien to my own way of working the list. And I often wish that I could stand over someone's shoulder so I could tell them what they are doing wrong. >>
It's a combination of many things that tends to make me crawl:
1. Lots of tasks. SF seems to be topping out around 400-450 for me, with 25-30 active pages - currently it's in a down-trend since lots pages are getting dismissed the last couple days (C2 overload). My speed feels pretty good generally -- but even with a good speed it can take some time to work through that many active pages.
2. Heavy meetings 2-3 days per week -- limited discretionary time on those days. Column 2 tends to get overloaded on those days, since I am not moving forward very quickly. In a morning filled with meetings, I can't make any progress actioning a page, and just stay on that page. Meanwhile the inflow of urgent items continues -- some of them generated by the meetings themselves, some of them just the usual occasional email that requires urgent action, and some of them triggered by recurring reminders. These tend to pile up in Column 2 on the Next Page. So even if I have an hour or two of discretionary time at lunchtime, it's maybe enough to clear through Column 2 of the Current Page and the Next Page, and maybe knock out a handful of Column 1 items in the process. But then the rest of the day is filled with meetings again. So, on these meeting-heavy days, there's just no time to move more than 2-3 pages (at most).
3. I have maybe 2 days per week with at least 4-6 hours of discretionary time, so I can make good progress on those days. But I do usually have 1 or 2 largish projects in progress, and "little and often" typically means 20-60 minutes per iteration -- which means 20-60 minutes per page turn, just on those projects. The most optimistic case would be 6 hours of discretionary time, and 20 minutes per iteration. If I worked on absolutely nothing else, I'd get through 18 pages like this. (Ie., working for 20 minutes at a time on this Column 2 task, then pushing the task forward to the next page.) My current list has 21 active pages, so that's not even 1 cycle through the whole list. And of course, other items DO stand out and require attention -- so on a good productive day I can typically get through 4-8 pages of my list, thus cycling through the whole thing once or twice a week.
4. On weekends I have a variable amount of time, usually devoted to home and family projects (all in the same SF list as my work tasks). I usually have a lot of discretionary time but sometimes we are out all day and I don't have any time to work my list. So the pattern is pretty similar to what I described above.
Anyway, Mark, does this answer your question on why this happens?
I have found it to be a big problem if I NEVER cycle through the list, always chasing the end, etc. But for me, cycling through the list once or twice a week seems to be just fine. It works great, gives me a good balance between "urgent" and "important", as well as between the easy one-offs and the harder, larger projects.
<< I always have a problem envisaging what it is that causes crawlers to crawl because it is so alien to my own way of working the list. And I often wish that I could stand over someone's shoulder so I could tell them what they are doing wrong. >>
It's a combination of many things that tends to make me crawl:
1. Lots of tasks. SF seems to be topping out around 400-450 for me, with 25-30 active pages - currently it's in a down-trend since lots pages are getting dismissed the last couple days (C2 overload). My speed feels pretty good generally -- but even with a good speed it can take some time to work through that many active pages.
2. Heavy meetings 2-3 days per week -- limited discretionary time on those days. Column 2 tends to get overloaded on those days, since I am not moving forward very quickly. In a morning filled with meetings, I can't make any progress actioning a page, and just stay on that page. Meanwhile the inflow of urgent items continues -- some of them generated by the meetings themselves, some of them just the usual occasional email that requires urgent action, and some of them triggered by recurring reminders. These tend to pile up in Column 2 on the Next Page. So even if I have an hour or two of discretionary time at lunchtime, it's maybe enough to clear through Column 2 of the Current Page and the Next Page, and maybe knock out a handful of Column 1 items in the process. But then the rest of the day is filled with meetings again. So, on these meeting-heavy days, there's just no time to move more than 2-3 pages (at most).
3. I have maybe 2 days per week with at least 4-6 hours of discretionary time, so I can make good progress on those days. But I do usually have 1 or 2 largish projects in progress, and "little and often" typically means 20-60 minutes per iteration -- which means 20-60 minutes per page turn, just on those projects. The most optimistic case would be 6 hours of discretionary time, and 20 minutes per iteration. If I worked on absolutely nothing else, I'd get through 18 pages like this. (Ie., working for 20 minutes at a time on this Column 2 task, then pushing the task forward to the next page.) My current list has 21 active pages, so that's not even 1 cycle through the whole list. And of course, other items DO stand out and require attention -- so on a good productive day I can typically get through 4-8 pages of my list, thus cycling through the whole thing once or twice a week.
4. On weekends I have a variable amount of time, usually devoted to home and family projects (all in the same SF list as my work tasks). I usually have a lot of discretionary time but sometimes we are out all day and I don't have any time to work my list. So the pattern is pretty similar to what I described above.
Anyway, Mark, does this answer your question on why this happens?
I have found it to be a big problem if I NEVER cycle through the list, always chasing the end, etc. But for me, cycling through the list once or twice a week seems to be just fine. It works great, gives me a good balance between "urgent" and "important", as well as between the easy one-offs and the harder, larger projects.
Reply by Seraphim
Anthony wrote:
<< I really struggle to dismiss, and I "game" the system to avoid dismissing. ... That said, the system still works really well for me in terms of being productive - its just that I'm conscious that it could be a whole lot more powerful. >>
Yes, I also found that the mechanics of "standing out" and the handling of urgent and unfinished in Column 2 alone are a work of genius, and a very powerful TM system even without dismissal. But the dismissal mechanism is worthy of a Nobel prize. Once you start getting the hang of dismissal, it increases the power of the system by an order of magnitude.
<< I really struggle to dismiss, and I "game" the system to avoid dismissing. ... That said, the system still works really well for me in terms of being productive - its just that I'm conscious that it could be a whole lot more powerful. >>
Yes, I also found that the mechanics of "standing out" and the handling of urgent and unfinished in Column 2 alone are a work of genius, and a very powerful TM system even without dismissal. But the dismissal mechanism is worthy of a Nobel prize. Once you start getting the hang of dismissal, it increases the power of the system by an order of magnitude.
Reply by Seraphim
Mark Forster wrote:
<< However just because you are working "intuitively" doesn't mean that you have no control over what you are doing. You can instruct your intuition so that it achieves what you want it to. In particular you need to instruct your intuition about what speed it should be going at. There is a continuum between CRAWL and RACE, and you should be considerably nearer the RACE end than the CRAWL end. It's actually no more difficult to decide to speed up while doing SF than it is to decide to quicken your pace when you are walking down the street. >>
I've struggled with this. If I notch up the pressure to go faster, I find myself working on the easy stuff and neglecting the weightier matters.
For example, I've used a timer to help train my intuition to go faster (my suggestion #2, at the top of this post). And it does seem to help, almost magically in fact. But after a bit I began to notice a growing tendency to neglect the weightier projects that need more sustained attention and thought. I just couldn't "settle down" to spend 20-40 minutes on these larger tasks, since it would reduce my forward progress through the list. I'd feel itchy and restless and couldn't really concentrate on the large task. I'd try to convince myself that I was just trying to "clear the deck" of all the easy one-off tasks, and then I'd be able to concentrate on the larger tasks. But that just never really happened -- there is no end of the easy one-off tasks, it seems!
It seems a good balance is to follow one's own natural inclinations and intuition, in regard to "standing out" and "work as long as you want", but use exercises like the timer to broaden one's horizons, challenge one's assumptions, and examine what one is really capable of doing. There are always trade-offs and we need to find the right balance between them that works best for our own situation.
<< However just because you are working "intuitively" doesn't mean that you have no control over what you are doing. You can instruct your intuition so that it achieves what you want it to. In particular you need to instruct your intuition about what speed it should be going at. There is a continuum between CRAWL and RACE, and you should be considerably nearer the RACE end than the CRAWL end. It's actually no more difficult to decide to speed up while doing SF than it is to decide to quicken your pace when you are walking down the street. >>
I've struggled with this. If I notch up the pressure to go faster, I find myself working on the easy stuff and neglecting the weightier matters.
For example, I've used a timer to help train my intuition to go faster (my suggestion #2, at the top of this post). And it does seem to help, almost magically in fact. But after a bit I began to notice a growing tendency to neglect the weightier projects that need more sustained attention and thought. I just couldn't "settle down" to spend 20-40 minutes on these larger tasks, since it would reduce my forward progress through the list. I'd feel itchy and restless and couldn't really concentrate on the large task. I'd try to convince myself that I was just trying to "clear the deck" of all the easy one-off tasks, and then I'd be able to concentrate on the larger tasks. But that just never really happened -- there is no end of the easy one-off tasks, it seems!
It seems a good balance is to follow one's own natural inclinations and intuition, in regard to "standing out" and "work as long as you want", but use exercises like the timer to broaden one's horizons, challenge one's assumptions, and examine what one is really capable of doing. There are always trade-offs and we need to find the right balance between them that works best for our own situation.
Reply by Bernie
<< And I often wish that I could stand over someone's shoulder so I could tell them what they are doing wrong.>>
Mark,
I often wish I could watch over your shoulder to learn what you are doing right! :)
Over the last two months, SF has markedly improved the flow and balance of my work, but the remaining puzzle is in these large projects of Hugo's variety:
<<... the "little" part of "little and often" can easily be 45min to an hour (minimum), and the "work as long you feel like" can to for 4 or 5 hours without even noticing (fully focused; in the "zone"). ... stoping work would imply having to repeat a lot of the preparation again when you came back to it ... or even doing it all over again >>
On my projects that are *not* like Hugo's above, I flip the page every time I get up for a drink or to answer the phone or anything, and SF hums along nicely, more successfully than any other system I've used. But on projects like Hugo's above, I find myself mentally figuring them, even talking them through to myself as I get the drink, and when I sit down again, I cannot stomach a page flip and having to work on some piddly thing that will stop all the gears in my mind. Those gears can take quite a while to restart!
I do have room for improvement in dismissal. Perhaps the answer is simply that I need to let more of those pages be dismissed when I am working a big project? I.e., when I come back from that drink, unless I see something truly trivial that I can do without stopping the gears (it would have to be as trivial as getting that drink--perhaps tossing out a piece of junk mail), then the page gets dismissed; so be it. By the end of my five hours, I am easily five pages lighter. I guess that would truly reflect the reality of that situation and allow the list to respond by pruning itself.
Besides getting a drink, there is also time-boxing to help us take predictable breaks in these projects. Breaks every 45 min. or so tend to help me; when I return I usually have better ideas even though I wasn't aware of being stuck or off track. But still any Col.1 tasks picked up in between would have to be *extremely* lightweight, and so I'd be dismissing quite a few pages. As I write this, I feel more and more definite that it solves my puzzle!
Am I getting warmer or colder? Thanks everyone for your help. I am finding this thread critical right now!
Mark,
I often wish I could watch over your shoulder to learn what you are doing right! :)
Over the last two months, SF has markedly improved the flow and balance of my work, but the remaining puzzle is in these large projects of Hugo's variety:
<<... the "little" part of "little and often" can easily be 45min to an hour (minimum), and the "work as long you feel like" can to for 4 or 5 hours without even noticing (fully focused; in the "zone"). ... stoping work would imply having to repeat a lot of the preparation again when you came back to it ... or even doing it all over again >>
On my projects that are *not* like Hugo's above, I flip the page every time I get up for a drink or to answer the phone or anything, and SF hums along nicely, more successfully than any other system I've used. But on projects like Hugo's above, I find myself mentally figuring them, even talking them through to myself as I get the drink, and when I sit down again, I cannot stomach a page flip and having to work on some piddly thing that will stop all the gears in my mind. Those gears can take quite a while to restart!
I do have room for improvement in dismissal. Perhaps the answer is simply that I need to let more of those pages be dismissed when I am working a big project? I.e., when I come back from that drink, unless I see something truly trivial that I can do without stopping the gears (it would have to be as trivial as getting that drink--perhaps tossing out a piece of junk mail), then the page gets dismissed; so be it. By the end of my five hours, I am easily five pages lighter. I guess that would truly reflect the reality of that situation and allow the list to respond by pruning itself.
Besides getting a drink, there is also time-boxing to help us take predictable breaks in these projects. Breaks every 45 min. or so tend to help me; when I return I usually have better ideas even though I wasn't aware of being stuck or off track. But still any Col.1 tasks picked up in between would have to be *extremely* lightweight, and so I'd be dismissing quite a few pages. As I write this, I feel more and more definite that it solves my puzzle!
Am I getting warmer or colder? Thanks everyone for your help. I am finding this thread critical right now!
Reply by Hugo Ferreira
Mark,
I meant "problem" in the sense of this thread, i.e. "cycling the list faster".
SF has been immensely helpful for all the other "stuff" both at my company (clients, paperwork, etc) and at home, but the bulk of those tasks are the kind where "little & often" fits like a glove: tasks where in the past I "didn't have time right now" end up being worked on and advancing because I can "just take the folder out". It's a great feeling.
But when I reach those "Big Rocks" on the list, progress stops to a halt and it can take days to advance a couple of pages. They are part of my job (and something I greatly enjoy) but running my (very small) company is also and during those times I worry that I might be droping the ball somewhere else on the list.
I meant "problem" in the sense of this thread, i.e. "cycling the list faster".
SF has been immensely helpful for all the other "stuff" both at my company (clients, paperwork, etc) and at home, but the bulk of those tasks are the kind where "little & often" fits like a glove: tasks where in the past I "didn't have time right now" end up being worked on and advancing because I can "just take the folder out". It's a great feeling.
But when I reach those "Big Rocks" on the list, progress stops to a halt and it can take days to advance a couple of pages. They are part of my job (and something I greatly enjoy) but running my (very small) company is also and during those times I worry that I might be droping the ball somewhere else on the list.
Reply by Hugo Ferreira
Bernie,
Yes, I think you understood the situation perfectly :-)
Recently I segregated "errands", "calls" and "waiting" out of SF and into post-it notes in my notebook inside cover, and I like the way it streamlined the SF list.
Just thought that maybe moving this "Big Rocks" out and replacing with a "have time to focus?" on the list might help by knowing that when you return to the list it'll be streamlined and without tasks that standout to take half your day away.
This kind of segregation my also go well together with allocating time blocks for this long focused tasks (although time blocking hasn't worked well for me in the past).
I'm now trying the "Snooze SF3" tweak Mark mentioned in another thread, so I'll just see how this next week pans out with it in place.
Yes, I think you understood the situation perfectly :-)
Recently I segregated "errands", "calls" and "waiting" out of SF and into post-it notes in my notebook inside cover, and I like the way it streamlined the SF list.
Just thought that maybe moving this "Big Rocks" out and replacing with a "have time to focus?" on the list might help by knowing that when you return to the list it'll be streamlined and without tasks that standout to take half your day away.
This kind of segregation my also go well together with allocating time blocks for this long focused tasks (although time blocking hasn't worked well for me in the past).
I'm now trying the "Snooze SF3" tweak Mark mentioned in another thread, so I'll just see how this next week pans out with it in place.
Reply by Mark Forster
This is a general reply as too many people have made the same points to answer them individually:
1) If what you are doing produces the results you want, then it doesn't matter what speed you are moving at.
2) SF is a system for controlling discretionary time. If you don't have any discretionary time, then the system isn't going to work. The solution is to increase your discretionary time. There are many ways of doing this, but the place to start is the number of meetings you have.
3) I've never been a programmer so I don't know whether it's actually the case that taking a break means that you have to start again from scratch. It would be contrary to my experience in every other field of mental activity, where taking a break improves one's thinking. However if it is the case then I suggest that the best way forward is to take programming out of discretionary time and make it a scheduled activity.
4) If you don't follow the dismissal rules, you can forget about making SF work.
1) If what you are doing produces the results you want, then it doesn't matter what speed you are moving at.
2) SF is a system for controlling discretionary time. If you don't have any discretionary time, then the system isn't going to work. The solution is to increase your discretionary time. There are many ways of doing this, but the place to start is the number of meetings you have.
3) I've never been a programmer so I don't know whether it's actually the case that taking a break means that you have to start again from scratch. It would be contrary to my experience in every other field of mental activity, where taking a break improves one's thinking. However if it is the case then I suggest that the best way forward is to take programming out of discretionary time and make it a scheduled activity.
4) If you don't follow the dismissal rules, you can forget about making SF work.
Reply by Seraphim
On programming -- I used to think "little and often" didn't work for this. But over the last couple of years I found that's just not quite true. Both AF and SF have given me plenty of practice finding ways to mentally bookmark my programming work, so it's not so hard to stop and start up again. And like Mark said, "taking a break improves one's thinking".
Programming can be like an addiction -- you develop some code, you try it out, it works but not quite, you tweak it, it works better but still not exactly what you want, you keep developing, keep tweaking, finally you are happy with the results. This process gives you immediate feedback, but like a gambling addiction, the results are not 100% consistent. So you keep developing, tweaking, testing till you get the results you want, but even when you're "done" it NEVER feels really perfect, you KNOW there are better ways to abstract the code into reusable modules, genericize it better so you can reuse the modules in other projects, etc. And that keeps drawing you back.
This process is perfectly descriptive of addictive behavior.
The best way to train a dog (so I've read) is to give it a reward for the desired behavior about 60% of the time. This is actually far more effective than giving it a reward 100% of the time. Programming is like that. If you wrote some code and it always worked the first time, it would be mechanical and boring, rather than addictive.
I only do some programming occasionally, in Perl or XML development or VB macros -- I'm not a full-time software developer, so maybe it's different for you full-time pros out there. But AF / SF taught me that a really big part of the "programmer's high" when you feel like you are "in the zone" is really a kind of addiction, like I tried to describe above, and not a real working necessity. AF/SF can help you get over that habit and work effectively doing "little and often". I've found my code is actually done much faster and with better quality this way. But then again, I'm not a full-timer so maybe it doesn't really apply...
Programming can be like an addiction -- you develop some code, you try it out, it works but not quite, you tweak it, it works better but still not exactly what you want, you keep developing, keep tweaking, finally you are happy with the results. This process gives you immediate feedback, but like a gambling addiction, the results are not 100% consistent. So you keep developing, tweaking, testing till you get the results you want, but even when you're "done" it NEVER feels really perfect, you KNOW there are better ways to abstract the code into reusable modules, genericize it better so you can reuse the modules in other projects, etc. And that keeps drawing you back.
This process is perfectly descriptive of addictive behavior.
The best way to train a dog (so I've read) is to give it a reward for the desired behavior about 60% of the time. This is actually far more effective than giving it a reward 100% of the time. Programming is like that. If you wrote some code and it always worked the first time, it would be mechanical and boring, rather than addictive.
I only do some programming occasionally, in Perl or XML development or VB macros -- I'm not a full-time software developer, so maybe it's different for you full-time pros out there. But AF / SF taught me that a really big part of the "programmer's high" when you feel like you are "in the zone" is really a kind of addiction, like I tried to describe above, and not a real working necessity. AF/SF can help you get over that habit and work effectively doing "little and often". I've found my code is actually done much faster and with better quality this way. But then again, I'm not a full-timer so maybe it doesn't really apply...
Reply by Seraphim
Mark Forster wrote:
<< If you don't have any discretionary time, then the system isn't going to work. The solution is to increase your discretionary time. There are many ways of doing this, but the place to start is the number of meetings you have. >>
Yes, this is a constant battle. AF/SF have been helpful with this as well. These kinds of tasks can be helpful:
+ Do I really need to attend meeting XXX?
+ Can someone else attend meeting YYY instead of me?
+ Can we cancel recurring meeting ZZZ?
+ Can we consolidate meetings AAA and BBB?
+ Can we meet monthly instead of weekly?
Or simply:
+ Reduce calendar commitments
+ Clean up calendar
+ Delete meetings you don't HAVE to attend
Just in the past two months or so, I've reduced my meeting load significantly, mostly the result of using techniques like this. Part of the success with this is due to the work changing, so one or two recurring meetings got cancelled. But a bigger part is due to re-thinking why I am attending so many meetings, or even worse, why I am RUNNING so many meetings. We can't avoid them completely but we can make them more effective and less of a time sink.
<< If you don't have any discretionary time, then the system isn't going to work. The solution is to increase your discretionary time. There are many ways of doing this, but the place to start is the number of meetings you have. >>
Yes, this is a constant battle. AF/SF have been helpful with this as well. These kinds of tasks can be helpful:
+ Do I really need to attend meeting XXX?
+ Can someone else attend meeting YYY instead of me?
+ Can we cancel recurring meeting ZZZ?
+ Can we consolidate meetings AAA and BBB?
+ Can we meet monthly instead of weekly?
Or simply:
+ Reduce calendar commitments
+ Clean up calendar
+ Delete meetings you don't HAVE to attend
Just in the past two months or so, I've reduced my meeting load significantly, mostly the result of using techniques like this. Part of the success with this is due to the work changing, so one or two recurring meetings got cancelled. But a bigger part is due to re-thinking why I am attending so many meetings, or even worse, why I am RUNNING so many meetings. We can't avoid them completely but we can make them more effective and less of a time sink.
Reply by DavidC
The themes of ...
- fewer meetings
- reluctance to interrupt the flow states software developers and other creative types can get into
.... are linked in the article at http://www.paulgraham.com/makersschedule.html
- fewer meetings
- reluctance to interrupt the flow states software developers and other creative types can get into
.... are linked in the article at http://www.paulgraham.com/makersschedule.html
Reply by Bernie
<> [Mark Forster]
<< On programming -- I used to think "little and often" didn't work for this. But over the last couple of years I found that's just not quite true ... This process is perfectly descriptive of addictive behavior.>> [Seraphim]
Mark and Seraphim, you are right on the money. Having written code myself "in the trenches" for two decades, I still lapse into the feeling that, "I just can't take a break, it doesn't work like that." Yet, though the feeling is very real and consuming (and precisely as Seraphim describes), I find time and again that it pays to take a step back using some kind of time-boxing or other means of interruption. Not every 5 minutes, of course. But every 45 to 90 is very helpful. At my last programming job, our manager slyly coaxed regular breaks out of us by bringing in a ping-pong table. He knew what he was doing!
I can hardly wait for Monday to try out certain time-boxing ideas that seem well-suited to work within SuperFocus. After some road-testing, I will share them here. Until then, to all addicted writers of code on this forum, I would urge you to *take breaks* whether it comes at the hands of SuperFocus or a ping-pong table.
<< On programming -- I used to think "little and often" didn't work for this. But over the last couple of years I found that's just not quite true ... This process is perfectly descriptive of addictive behavior.>> [Seraphim]
Mark and Seraphim, you are right on the money. Having written code myself "in the trenches" for two decades, I still lapse into the feeling that, "I just can't take a break, it doesn't work like that." Yet, though the feeling is very real and consuming (and precisely as Seraphim describes), I find time and again that it pays to take a step back using some kind of time-boxing or other means of interruption. Not every 5 minutes, of course. But every 45 to 90 is very helpful. At my last programming job, our manager slyly coaxed regular breaks out of us by bringing in a ping-pong table. He knew what he was doing!
I can hardly wait for Monday to try out certain time-boxing ideas that seem well-suited to work within SuperFocus. After some road-testing, I will share them here. Until then, to all addicted writers of code on this forum, I would urge you to *take breaks* whether it comes at the hands of SuperFocus or a ping-pong table.
Reply by Seraphim
Bernie wrote - << I can hardly wait for Monday to try out certain time-boxing ideas that seem well-suited to work within SuperFocus >>
I know that time boxing can work great for some people -- but it never works for me. If I want to guarantee that I will NOT work on something, then I make a time-box for it. :-)
But I have found that using a timer helps quite a bit. If I have a largish task that I know will suck me in for hours at a time if I am not careful, then I enter the task into SF, and set a time limit. When the task stands out, I start the timer for 45 minutes or 90 minutes or whatever seems to be appropriate. When the timer beeps, then I wrap things up and move on. It might take me a few minutes to actually stop and wrap things up, but it's much better than going on and on for hours and hours.
One thing I haven't tried yet but just occurred to me: You could write several different time limits into SF and see which ones stand out:
- Programming Project NNN, max 30 minutes
- Programming Project NNN, max 45 minutes
- Programming Project NNN, max 60 minutes
- Programming Project NNN, max 90 minutes
etc.
It would be interesting to see if some of these stand out more than others would.
I know that time boxing can work great for some people -- but it never works for me. If I want to guarantee that I will NOT work on something, then I make a time-box for it. :-)
But I have found that using a timer helps quite a bit. If I have a largish task that I know will suck me in for hours at a time if I am not careful, then I enter the task into SF, and set a time limit. When the task stands out, I start the timer for 45 minutes or 90 minutes or whatever seems to be appropriate. When the timer beeps, then I wrap things up and move on. It might take me a few minutes to actually stop and wrap things up, but it's much better than going on and on for hours and hours.
One thing I haven't tried yet but just occurred to me: You could write several different time limits into SF and see which ones stand out:
- Programming Project NNN, max 30 minutes
- Programming Project NNN, max 45 minutes
- Programming Project NNN, max 60 minutes
- Programming Project NNN, max 90 minutes
etc.
It would be interesting to see if some of these stand out more than others would.
Reply by Bernie
Seraphim, you just described a good portion of my plan for next week.
I think the "time boxing" that doesn't work for you is what I'd call "scheduling." That is, designating a certain arbitrary time of day to do Project X. That is as unappealing to me as it seems to be to you. Its arbitrariness and pre-calculatedness is the exact opposite of SF's "standing out."
What I call "time boxing" is simply that I will set a timer when I start working one of these projects. This lets me survey the landscape *before* all the gears are turning, to estimate how long I can afford to get lost in the Project X time warp. Then I set the timer and allow myself to get lost in it. The hard part is taking the timer seriously when it rings. Naturally, if I get stuck before it rings, I can stop at any point and turn to SF.
I have time-boxed in the past, and it always runs great until I start disrespecting the timer. That's when it falls apart. The other problem is that feeling of "what now?" in between time boxes. Before SF, it wasn't always clear how to fit something gainful into those in-between times.
Btw, for any "Pomodoro" fans out there, my only objections to The Pomodoro Method are that the 25-minute box is just not long enough, and I don't want the entire day to be time-boxed. So you can think of this whole idea as modified Pomodoro, injected with performance-enhancing SuperFocus, if you want. Though to me, SF feels like the heart of the system.
I think the "time boxing" that doesn't work for you is what I'd call "scheduling." That is, designating a certain arbitrary time of day to do Project X. That is as unappealing to me as it seems to be to you. Its arbitrariness and pre-calculatedness is the exact opposite of SF's "standing out."
What I call "time boxing" is simply that I will set a timer when I start working one of these projects. This lets me survey the landscape *before* all the gears are turning, to estimate how long I can afford to get lost in the Project X time warp. Then I set the timer and allow myself to get lost in it. The hard part is taking the timer seriously when it rings. Naturally, if I get stuck before it rings, I can stop at any point and turn to SF.
I have time-boxed in the past, and it always runs great until I start disrespecting the timer. That's when it falls apart. The other problem is that feeling of "what now?" in between time boxes. Before SF, it wasn't always clear how to fit something gainful into those in-between times.
Btw, for any "Pomodoro" fans out there, my only objections to The Pomodoro Method are that the 25-minute box is just not long enough, and I don't want the entire day to be time-boxed. So you can think of this whole idea as modified Pomodoro, injected with performance-enhancing SuperFocus, if you want. Though to me, SF feels like the heart of the system.
Reply by Anthony
For the past two days I've been ruthless about Dismissal. And guess what - I'm beginning to feel the power of SF (not that it wasn't working well for me before). And my world hasn't fallen apart because I've dismissed tasks.....
Hardly a revelation to you all, but not easy for me because I feel the need to "do" everything that I think needs to be done.
Seraphim - thanks for this post, which prompted me into action
Hardly a revelation to you all, but not easy for me because I feel the need to "do" everything that I think needs to be done.
Seraphim - thanks for this post, which prompted me into action
Reply by jFenter
Similar to DavidC's link, Joel Spolsky (Joel on Software) wrote about the problems programmers have with "little and often". http://www.joelonsoftware.com/articles/fog0000000022.html
I'm a "full-time pro" at programming. (Not quite two decades like Bernie, but pretty close to it.) I've seen that its the depth of focus that big programming projects require that causes the problems. Taking a break from that is fine and healthy as long as I don't have to switch contexts and lose all of the preparation and "landscape surveying" that I had just done.
Don't get me wrong. Non-programming tasks also require focus and have depth and intensity. It's just that I've seen that my state of mind while programming is like a house of cards: intricate, detailed, tedious to build and highly fragile. If I don't take a picture of that card house (fix the bug... complete a module...) then switching to a new context knocks it all down.
I'm a "full-time pro" at programming. (Not quite two decades like Bernie, but pretty close to it.) I've seen that its the depth of focus that big programming projects require that causes the problems. Taking a break from that is fine and healthy as long as I don't have to switch contexts and lose all of the preparation and "landscape surveying" that I had just done.
Don't get me wrong. Non-programming tasks also require focus and have depth and intensity. It's just that I've seen that my state of mind while programming is like a house of cards: intricate, detailed, tedious to build and highly fragile. If I don't take a picture of that card house (fix the bug... complete a module...) then switching to a new context knocks it all down.
Reply by Mark Forster
jFenter:
Joel's post is interesting as usual, but when he's talking about multitasking he is talking about multi-tasking programming projects. I can see that might cause problems. But even programmers must have other things to do than just programming. Or don't they?
Joel's post is interesting as usual, but when he's talking about multitasking he is talking about multi-tasking programming projects. I can see that might cause problems. But even programmers must have other things to do than just programming. Or don't they?
Reply by jFenter
I have forgotten to eat before. I have chosen not to eat before. ;)
Based it on my own past experiences, some tasks can be done without much thinking: watering the plants, taking and writing down a helpdesk call, /maybe/ filling out a day's timesheet. While programming, my mind has "grabbed on" to the code and its context. As long as my mind doesn't have to grab on to something new, then yes, I am able to multitask. I am able to take a break and "let go", because my subconscious doesn't really let go at all. That's why I can come back after a break with fresh ideas. If I have to try to fix that helpdesk issue, or if I have to think about an entire week's timesheet, then my mind has to grab on to something new and I've toppled the house of cards that allowed me to do the programming.
"Little and often" /can/ work for a programmer as long as the programmer's subconscious can stay within the context. (I keep coming back to that word.)
Based it on my own past experiences, some tasks can be done without much thinking: watering the plants, taking and writing down a helpdesk call, /maybe/ filling out a day's timesheet. While programming, my mind has "grabbed on" to the code and its context. As long as my mind doesn't have to grab on to something new, then yes, I am able to multitask. I am able to take a break and "let go", because my subconscious doesn't really let go at all. That's why I can come back after a break with fresh ideas. If I have to try to fix that helpdesk issue, or if I have to think about an entire week's timesheet, then my mind has to grab on to something new and I've toppled the house of cards that allowed me to do the programming.
"Little and often" /can/ work for a programmer as long as the programmer's subconscious can stay within the context. (I keep coming back to that word.)
Reply by Tijl Kindt
I am a programmer myself, and I have to agree with jFenter.
Some days when I am really *in the zone*, I can program for 12 hours straight with only a 15 minute break for lunch. Having to work on other things can ruin the flow completely and even when I try to do other things, my mind would just keep working on the program. I'm not sure whether this is really the healthiest or most productive way to do this kind of stuff in the long term, but they definitely are productive days. When a day like this happens, basically my SF list is put on pause and I only work on the programming until I'm exhausted or frustrated because something isn't doing what I want it to do ;).
Some days when I am really *in the zone*, I can program for 12 hours straight with only a 15 minute break for lunch. Having to work on other things can ruin the flow completely and even when I try to do other things, my mind would just keep working on the program. I'm not sure whether this is really the healthiest or most productive way to do this kind of stuff in the long term, but they definitely are productive days. When a day like this happens, basically my SF list is put on pause and I only work on the programming until I'm exhausted or frustrated because something isn't doing what I want it to do ;).
Reply by Mark Forster
Tijl:
There have certainly been times when I've worked for 12 hours straight at one thing, and sometimes it's been necessary. But more often it's because I haven't been working little and often on it up to then so I have had to put in a mammoth session to meet a deadline.
It's like a piano teacher saying "Practice a bit every day before the next lesson. Don't save it all up for the evening before."
The question is not whether working in huge sessions can be done. It's whether it's a good idea for it to be done that way.
I have a suspicion that computer programming is addictive in the same way that some computer games are ("just one more shot at the highest score and then I'll stop").
I'm not a programmer, but I have run time management courses in software firms and it was noticeable that the programmers who objected most strongly to taking breaks were also the ones who their bosses thought had the worst time management. I hope that doesn't apply to my esteemed readers!
There have certainly been times when I've worked for 12 hours straight at one thing, and sometimes it's been necessary. But more often it's because I haven't been working little and often on it up to then so I have had to put in a mammoth session to meet a deadline.
It's like a piano teacher saying "Practice a bit every day before the next lesson. Don't save it all up for the evening before."
The question is not whether working in huge sessions can be done. It's whether it's a good idea for it to be done that way.
I have a suspicion that computer programming is addictive in the same way that some computer games are ("just one more shot at the highest score and then I'll stop").
I'm not a programmer, but I have run time management courses in software firms and it was noticeable that the programmers who objected most strongly to taking breaks were also the ones who their bosses thought had the worst time management. I hope that doesn't apply to my esteemed readers!
Reply by Alan Baljeu
"had the worst". Of course they did. How can you ever get all duties covered if you stick to one task exclusively for two days solid?
Reply by Tijl Kindt
Mostly these mammoth sessions were personal hobby projects to be honest. But I've also had them for some university projects.
True. When they hurt your other work, the are not a good idea, but if they don't hurt your SF flow for the rest of the week or are hurtful in some other way, I do think they are some of the most productive days I ever have.
Definitely, though with programming it's usually "I really have to get that bug fixed!"... and then when you get that bug fixed, another one pops up :P.
Reply by jFenter
While it's true that there have been times when I've procrastinated and had to cram, that is not the motivator behind most of my "mammoth sessions". Like Tijl Kindt, it can happen with personal projects that have no deadlines. Yes, there is a bit of an addictive quality to it, but that, too, I find to be a minor difficulty with the "little and often".
I would liken "programming" to running a jazz club. You have to make sure the acts get on stage at the right time. You have to remember who you advertised as the main show so you know what your customers expect. You have to keep in mind seating capacity and your inventory of whiskey. You have to remember who ordered what to eat and that its being prepared. All of this by yourself. And in the middle of the dinner rush, someone comes up to you and asks you what you got your wife for her birthday three years ago.
That's what a mid-morning meeting does to a programmer. That's what happens when I switch from "writing code" to "making follow-up calls with customers". I can take a smoke break while working the jazz club, but I can't switch gears and start thinking about non-jazz-club-stuff.
Reply by Cricket
I've only dabbled in programming and novel writing, but I've definitely felt the heady, addictive rush that Seraphim describes, and how hard it is to get back into the flow after a break.
A good exercise is to push yourself as far out of "giant teetering house of cards" mode as possible.
Try to keep the house as small and stable as possible. Take a few moments to look at each card before you add it. Does it have to be added to that house right now, or can it sit in a stack on the side (written in a notebook)? Can you turn the house into a tidy, stable stack before going home?
Doing one card (or at least one room) at a time helps me focus. Rather than chasing threads all over the place, leaving half-debugged sections everywhere, I can do one smaller section at a time and actually finish them. Program flow and calculations are easier to read without all the error and exception checking, and can be done with a horrid user interface. I write a bare-bones routine that works, and make a note of what format the data needs to be in.
It's also easier to come back to a project if each room is small and stable. I can write a pretty data-input section and I don't have to remember a thing about the calculations to do it. Then I find the user can't give me the data I assumed, so at least I didn't waste time doing all that error and exception checking.
When binge programming, everything else falls down. Then I have to spend a day doing catch-up on email and little things for other people, and everyone's upset. All time spent not prgramming is miserable.
A good exercise is to push yourself as far out of "giant teetering house of cards" mode as possible.
Try to keep the house as small and stable as possible. Take a few moments to look at each card before you add it. Does it have to be added to that house right now, or can it sit in a stack on the side (written in a notebook)? Can you turn the house into a tidy, stable stack before going home?
Doing one card (or at least one room) at a time helps me focus. Rather than chasing threads all over the place, leaving half-debugged sections everywhere, I can do one smaller section at a time and actually finish them. Program flow and calculations are easier to read without all the error and exception checking, and can be done with a horrid user interface. I write a bare-bones routine that works, and make a note of what format the data needs to be in.
It's also easier to come back to a project if each room is small and stable. I can write a pretty data-input section and I don't have to remember a thing about the calculations to do it. Then I find the user can't give me the data I assumed, so at least I didn't waste time doing all that error and exception checking.
When binge programming, everything else falls down. Then I have to spend a day doing catch-up on email and little things for other people, and everyone's upset. All time spent not prgramming is miserable.
Reply by Mark Forster
jFenter:
I've run plenty of things which require a similar degree of organising to a jazz club, and basically everything you mention would be documented so that you can pick it up as required. You don't wing the acts getting on stage at the right time - you have a timed schedule which you refer to. You don't "remember" who you advertised as the main show - it's written in your event folder. And the same goes for the seating capacity, the inventory of whiskey, and the meal ordering. So if interruptions happen (and they are inevitable) you can deal with them and get back to what you need to be doing with the minimum disruption.
So that leads to the question whether the problem that (some?/all?) programmers have picking up where they left off is due to their not documenting what they are doing.
I've run plenty of things which require a similar degree of organising to a jazz club, and basically everything you mention would be documented so that you can pick it up as required. You don't wing the acts getting on stage at the right time - you have a timed schedule which you refer to. You don't "remember" who you advertised as the main show - it's written in your event folder. And the same goes for the seating capacity, the inventory of whiskey, and the meal ordering. So if interruptions happen (and they are inevitable) you can deal with them and get back to what you need to be doing with the minimum disruption.
So that leads to the question whether the problem that (some?/all?) programmers have picking up where they left off is due to their not documenting what they are doing.
Reply by jFenter
Gack! You speak of Documentation! The bane of programmers everywhere!
Does that answer your question? ;)
To be clear, I began looking into time- and task-management solutions /because/ of my disorganization and procrastination. GTD made me less freaked out, and SF actually makes me feel good. But no TM will help me with my disorganization-- my disorganization and lack of documentation frustrates my "little and often"-- my frustration (not my complaint... I'm honestly not complaining) shows me where I need to grow next. I'm just sharing my views here so that others can learn from the experience.
Thank you for bringing that to light, Mark. I don't know if you've hit the nail on the head, but it does deserve some serious thought. Does this mean I need to pay your consulting fee now? lol
Does that answer your question? ;)
To be clear, I began looking into time- and task-management solutions /because/ of my disorganization and procrastination. GTD made me less freaked out, and SF actually makes me feel good. But no TM will help me with my disorganization-- my disorganization and lack of documentation frustrates my "little and often"-- my frustration (not my complaint... I'm honestly not complaining) shows me where I need to grow next. I'm just sharing my views here so that others can learn from the experience.
Thank you for bringing that to light, Mark. I don't know if you've hit the nail on the head, but it does deserve some serious thought. Does this mean I need to pay your consulting fee now? lol
Reply by Alan Baljeu
I think part of the trouble is there's no established process for programming. It's not taught in schools. (Computer science is taught, but that's not the same thing.) Ideas are still fermenting on the topic. Here's an interesting idea for keeping track of what you're working on, and not getting lost in the house of cards:
http://mikadomethod.wordpress.com/book/
http://mikadomethod.wordpress.com/book/
Reply by Seraphim
jFenter wrote - << Does this mean I need to pay your consulting fee now? lol >>
Just click at the Paypal link in the top-left corner of the page. Which I haven't done lately myself. Thanks for the reminder!
Just click at the Paypal link in the top-left corner of the page. Which I haven't done lately myself. Thanks for the reminder!
Reply by Bernie
Speaking to the "programmer's house of cards":
This is an excellent image of what we go through, immersed in our software cubicles. I have built many a teetering monstrosity myself (including those delightful tours through Other People's Code), and I know all too well the grip that these structures naturally have on a programmer's mind. It feels as if I had better KEEP WORKING until it is 100% DONE, or I will never ever get all that detail back into my head without wasting precious hours. "Just write it down," they say? Bah! I will exhaust the company's supply of paper, and I wouldn't know where to start anyway, as I never took "Nineteen-dimensional diagramming 101" in college.
Despite all that, here is what I actually found when I began taking (forced!) breaks:
Taking notes on all my intricate ideas, it only took 5-10 minutes to capture enough information that I suddenly felt fine walking away from it. In fact, seeing just its major parts on paper turned out to be a relief, making the structure seem much less teetering and much less nineteen-dimensional—much less as if keeping track of it had anything to do with how soon I returned. Upon returning to my desk later, I found that various parts of my notes where (a) very effective reminders, (b) indecipherable, and (c) utterly silly. I would then proceed to recreate the entire house of cards in my head in a few more minutes, with fewer cards, placed much more effectively. My co-workers who gave it a try reported similar experiences. And we got really good at ping-pong.
If you haven't tried this, give it a week and see what happens. If it makes you three thousand percent less productive, tell your boss it's all my fault! ;) The ping-pong table is optional.
This is an excellent image of what we go through, immersed in our software cubicles. I have built many a teetering monstrosity myself (including those delightful tours through Other People's Code), and I know all too well the grip that these structures naturally have on a programmer's mind. It feels as if I had better KEEP WORKING until it is 100% DONE, or I will never ever get all that detail back into my head without wasting precious hours. "Just write it down," they say? Bah! I will exhaust the company's supply of paper, and I wouldn't know where to start anyway, as I never took "Nineteen-dimensional diagramming 101" in college.
Despite all that, here is what I actually found when I began taking (forced!) breaks:
Taking notes on all my intricate ideas, it only took 5-10 minutes to capture enough information that I suddenly felt fine walking away from it. In fact, seeing just its major parts on paper turned out to be a relief, making the structure seem much less teetering and much less nineteen-dimensional—much less as if keeping track of it had anything to do with how soon I returned. Upon returning to my desk later, I found that various parts of my notes where (a) very effective reminders, (b) indecipherable, and (c) utterly silly. I would then proceed to recreate the entire house of cards in my head in a few more minutes, with fewer cards, placed much more effectively. My co-workers who gave it a try reported similar experiences. And we got really good at ping-pong.
If you haven't tried this, give it a week and see what happens. If it makes you three thousand percent less productive, tell your boss it's all my fault! ;) The ping-pong table is optional.
Reply by Jeff N
I've been a programmer for almost 25 years now, so I thought I'd weigh in here.
Interestingly enough, I've found that programming is the one activity that I NEVER feel resistance to, and I that never have a hard time getting back in the "flow" with. It doesn't matter if it's been hours, days, or weeks since I left whatever I was working on--all I have to do is stare at the code for a few minutes and everything comes flooding back (together with all of the new ideas that my brain has been processing in the meantime).
Perhaps it's due to good practices like test-driven development (the fun way to write unit tests) and "obsessive-compulsive refactoring." I rather suspect, however, that my brain has some sort of reserved compartment for this kind of thing. I can recall details of nearly every piece of code I've written or touched in the last two years (and I've noticed that this is not generally true among my colleagues). When I have an active programming task, my mind is continually churning on it regardless of whatever else I might physically be doing or thinking about.
In contrast, an activity like writing is VERY hard for me to do "little and often" with. If it's been more than an hour since I last touched a piece of prose, it can take forever for me to get back into context (20-30 minutes of hard work). Working for 5-10 minutes only on a writing effort often produces zero forward progress. Thus, an interruption when writing often means a day or more delay in finishing. Hmmm . . .
Interestingly enough, I've found that programming is the one activity that I NEVER feel resistance to, and I that never have a hard time getting back in the "flow" with. It doesn't matter if it's been hours, days, or weeks since I left whatever I was working on--all I have to do is stare at the code for a few minutes and everything comes flooding back (together with all of the new ideas that my brain has been processing in the meantime).
Perhaps it's due to good practices like test-driven development (the fun way to write unit tests) and "obsessive-compulsive refactoring." I rather suspect, however, that my brain has some sort of reserved compartment for this kind of thing. I can recall details of nearly every piece of code I've written or touched in the last two years (and I've noticed that this is not generally true among my colleagues). When I have an active programming task, my mind is continually churning on it regardless of whatever else I might physically be doing or thinking about.
In contrast, an activity like writing is VERY hard for me to do "little and often" with. If it's been more than an hour since I last touched a piece of prose, it can take forever for me to get back into context (20-30 minutes of hard work). Working for 5-10 minutes only on a writing effort often produces zero forward progress. Thus, an interruption when writing often means a day or more delay in finishing. Hmmm . . .
Reply by Seraphim
I've been buried with meetings lately - necessary meetings, but at a significant sacrifice of discretionary time.
So I invoked Trick #2 (see #2 in my first post at the top of this thread) -- "give yourself a time limit to get through each page". I allowed 20 minutes per page. I thought this would work pretty well since most of the pages were "mature" and didn't have many tasks left on them.
An interesting thing happened. I was really behind in clearing my email, and that task got carried forward in Column 2 from page to page. And I use the rule, "Clear Column 2 before starting on Column 1."
So, on every page, I would work on clearing my email. And I would always get absorbed in it, not wanting to stop. Pretty soon my timer would beep, and I had to move on to the next page.
But since I hadn't done any Column 1 tasks, I had to dismiss everything in Column 1. I ended up dismissing about 300 tasks. I only have about 120 tasks remaining. My list feels so light and free!
I know there are a few tasks buried in those dismissed tasks that really do need to get done -- but I'll find them in the next day or two, and get them done. It should be pretty easy to do, with only 120 tasks on my list.
In the process of doing this, I also realized that my "stalagmite/stalactite" method of processing work and personal tasks wasn't really working right. I had been slowly realizing that the two different domains function at different speeds, at a different cadence. Generally I have more discretionary time at work than at home, so as I cycled through my pages, my work tasks would get processed pretty fast, but my personal tasks would lag behind, mostly untouched. Finally the pages would get dismissed, but the personal tasks really hadn't been processed enough to warrant dismissal. It just felt wrong.
My mass dismissals today really highlighted this issue and showed me what the problem was. So, as I moved through the pages, I copied several personal tasks to a new "home" SF book, dismissed the rest, and from now on, I'll be using two different books. I've been doing stalagmite/stalactite for so long that it may take some adjustment before I figure out how to work this way, but I'm looking forward to it.
So I invoked Trick #2 (see #2 in my first post at the top of this thread) -- "give yourself a time limit to get through each page". I allowed 20 minutes per page. I thought this would work pretty well since most of the pages were "mature" and didn't have many tasks left on them.
An interesting thing happened. I was really behind in clearing my email, and that task got carried forward in Column 2 from page to page. And I use the rule, "Clear Column 2 before starting on Column 1."
So, on every page, I would work on clearing my email. And I would always get absorbed in it, not wanting to stop. Pretty soon my timer would beep, and I had to move on to the next page.
But since I hadn't done any Column 1 tasks, I had to dismiss everything in Column 1. I ended up dismissing about 300 tasks. I only have about 120 tasks remaining. My list feels so light and free!
I know there are a few tasks buried in those dismissed tasks that really do need to get done -- but I'll find them in the next day or two, and get them done. It should be pretty easy to do, with only 120 tasks on my list.
In the process of doing this, I also realized that my "stalagmite/stalactite" method of processing work and personal tasks wasn't really working right. I had been slowly realizing that the two different domains function at different speeds, at a different cadence. Generally I have more discretionary time at work than at home, so as I cycled through my pages, my work tasks would get processed pretty fast, but my personal tasks would lag behind, mostly untouched. Finally the pages would get dismissed, but the personal tasks really hadn't been processed enough to warrant dismissal. It just felt wrong.
My mass dismissals today really highlighted this issue and showed me what the problem was. So, as I moved through the pages, I copied several personal tasks to a new "home" SF book, dismissed the rest, and from now on, I'll be using two different books. I've been doing stalagmite/stalactite for so long that it may take some adjustment before I figure out how to work this way, but I'm looking forward to it.
Reply by Meryl
Mass dismissals Seraphim? Didnt I recommend something like that to you a couple of months ago?
Reply by Nicole
Hi Seraphim,
interesting observation about the different speeds of home and work tasks, I was wondering the same myself. My worry about two different notebooks would be that sometimes I need to do a home-related task at work or vice versa (for example, a call to a company that has to be made during the day). How do you deal with that? Or is that not a problem in your way of working?
interesting observation about the different speeds of home and work tasks, I was wondering the same myself. My worry about two different notebooks would be that sometimes I need to do a home-related task at work or vice versa (for example, a call to a company that has to be made during the day). How do you deal with that? Or is that not a problem in your way of working?
Reply by Mark Forster
Nicole:
That's why I recommend keeping separate notebooks for separate locations, rather than separate subjects. It's where you are going to do the task that matters, not what it relates to.
That's why I recommend keeping separate notebooks for separate locations, rather than separate subjects. It's where you are going to do the task that matters, not what it relates to.
Reply by Nicole
Of course location is what determines which notebook it goes into, but what I was trying to say is that I sometimes run into tasks that could be done or should be considered at both locations. How to deal with that? Enter them in both notebooks?
Reply by Alan Baljeu
Both.
Reply by Jeff N
And if you don't want to carry around two physical notebooks, get a book with lots of pages and start your "second" notebook on a page halfway or 2/3 of the way through. That's what I've done with my Moleskine and it's been working great for several months.
(A little post-it flag or something can help you find the second notebook quickly.)
(A little post-it flag or something can help you find the second notebook quickly.)
Reply by Seraphim
Meryl - Perhaps you did, and perhaps it was very good advice. But I don't see any rules that say "Dismiss when Meryl recommends it." :-) Sometimes we need to learn things for ourselves. If I had just dismissed everything, or deleted and started over, I wouldn't have learned anything, and most likely would have been back to a gigantic list within a week, and would not have any real insight into how to deal with it.
Also, my main concern on that other thread was the lack of an explicit dynamic that prevents unending growth of the list. "Faster cycling" seems to be the best answer to that dilemma. And it's the "Faster cycling" that led directly to the "mass dismissal".
Also, my main concern on that other thread was the lack of an explicit dynamic that prevents unending growth of the list. "Faster cycling" seems to be the best answer to that dilemma. And it's the "Faster cycling" that led directly to the "mass dismissal".
Reply by Seraphim
Nicole - That's one of the kinks I need to work out. It's easy enough for my way of working to carry around both books in my backpack, and jot down some non-urgent task in the out-of-context book. For urgent tasks I'm just writing all tasks in C2 of the book I am working with.
Reply by Seraphim
Mark wrote -
<< That's why I recommend keeping separate notebooks for separate locations, rather than separate subjects. It's where you are going to do the task that matters, not what it relates to. >>
Separate locations doesn't really fit for me. For my day job, sometimes I work from home, sometimes I work from the office. It's the same work. I use the same computer, I have the same set of meetings, objectives, and tasks. And approximately the same daily hours of working time. So it makes sense to use one SF book for all that, and take it with me when I go to the office.
When I work from home, I do have some flexibility with my schedule, but really need to be focused on work during working hours. Physically I could play with my children, help my wife with her business, pay the bills, etc., but that would be an abuse of my employer's trust if it goes beyond the incidental.
For me, it's more of a matter of making a very clear distinction between "work time" and "personal time", and having a different SF book for each.
<< That's why I recommend keeping separate notebooks for separate locations, rather than separate subjects. It's where you are going to do the task that matters, not what it relates to. >>
Separate locations doesn't really fit for me. For my day job, sometimes I work from home, sometimes I work from the office. It's the same work. I use the same computer, I have the same set of meetings, objectives, and tasks. And approximately the same daily hours of working time. So it makes sense to use one SF book for all that, and take it with me when I go to the office.
When I work from home, I do have some flexibility with my schedule, but really need to be focused on work during working hours. Physically I could play with my children, help my wife with her business, pay the bills, etc., but that would be an abuse of my employer's trust if it goes beyond the incidental.
For me, it's more of a matter of making a very clear distinction between "work time" and "personal time", and having a different SF book for each.
Reply by Mark Forster
Seraphim:
Perhaps Meryl is working on the advice in Proverbs:
Give instruction to a wise man and he will be yet wiser
teach a righteous man and he will increase in learning.
Perhaps Meryl is working on the advice in Proverbs:
Give instruction to a wise man and he will be yet wiser
teach a righteous man and he will increase in learning.
Reply by Richard Stamper
Seraphim: The way I have handled the home/work context split is to use one notebook but turn it upside-down and back-to-front, so that the work tasks are at the front of the book and the home tasks are at the back but each are still written in a top-to-bottom, left-to-right manner. The whole notebook is a stalactite-stalagmite pair, in other words. This seems to work OK for me. Switching context is just a question of flipping the book over.
Reply by Seraphim
Richard - That sounds like a reasonable approach.